Ham Radio 2000

home *** CD-ROM | disk | FTP | other *** search

/ Ham Radio 2000 / Ham Radio 2000.iso / ham2000 / packet / mb1801 / install.doc < prev next >

Wrap

Text File | 1994-10-15 | 34KB | 721 lines

INSTALL.DOC This document is intended to be a guide for installing the Packet Radio BBS program developed by: Hank Oredson, W0RLI. 21390 Shannon Lane West Linn, OR 97068 It will look at the installation of the software on your computer system from the aspect of an upgrade and a complete new install. These instructions are at the end of this document. This document is based on Version 18.x but will include instructions for upgrading from previous versions of W0RLI. It also assumes that you have a working knowledge of QuarterDeck's DesqView and QEMM programs and DOS. Note: All of the parameters and suggestions are examples. This document is meant to serve as a guide in installing and running the software. REGIONAL COORDINATORS Several people have kindly volunteered to act as regional coordinators for questions, bug reports, etc. These are as of this writing: G4WPT @ GB7BNM - For the U.K. JA1KSO @ JA1KSO - For Japan and the Far East LU3AGJ @ LU3AGJ - For Latin America VE3GYQ @ VE3GYQ - For North America N6IYA @ N6IYA - For North America. This major distribution point and can provide the software on any flavor of 5 1/4 or 3 1/2 floppy disk. The mailbox software is more than 360k in size so if 360k diskettes are required please send two. Send a SASE diskette mailer and formatted diskettes to: John Smith, N6IYA 1060 Pine Drive Felton, CA 95018 Dial up services are available upon request. Contact John @ (408) 335-2034 Releases are sent to N6IYA for test and release and then are uploaded to: WA6RDH @ WA6RDH WA6RDH dialup system @ (916) 678-1535 CompuServe Compuserve Hamnet Forum - Software Library OPERATING ENVIRONMENT This Mailbox runs under DOS or OS/2 in conjunction with DESQView. The mailbox will also run multiple copies in the above mentioned multi-tasking environments. In its present interation it will require that the system run in conjuntion with G8BPQ's switch software and the TNC's in the KISS mode. It is possible to run up to 24 tasks and 20 Ports and all common files to the mailbox will be shared. Starting with version 16.0 many of the common functions were moved to SERVER resutlting in a smaller MB.EXE task but a larger SERVER task. In version 17.x many of the tasks that were once handled by MB.EXE have now been moved to additional program files that handle specific types of system tasks. The result is a modular system, smaller and faster executable files and a smaller SERVER.EXE. (1) FILE STRUCTURE Most of the files used by the Mailbox are can now be set to reside in seperate directories. The only thing that is currently hardwired is the message files themselves. These must reside in the \BBS directory. The remaining files are placed into directories and are used in accordance with the enviornmental variables as described below. (See OTHER FILES below for more details.) ENVIRONMENTAL VARIABLES The executable files (.EXE and .COM) can be placed in a separate sub-directory. The easiest installation is to place all the Mailbox files into the \BBS directory. Any remaining file structure will be created upon startup of the system based on the entries in DIRS.MB. Starting in version 16.8 environmental variables can be setup in your autoexec.bat file that allow the placement of the various config files, database files, log files and temporary files into their own subdirectories to speed up the system processing. See OTHER FILES below for more details. SYSTEM REQUIREMENTS The minimum system requirements that are needed are: It is recommended that the code be run on a 386 or better. The number of ports, port speed and the number of tasks that can be run depend on the speed of the system and the amount of memory that you have. Assuming a 1200 baud Radio data rate, 9600 baud TNC to computer data rate the following guidelines apply: On a fast 386 with 4mb of memory at least 8 ports with 12 tasks has been tested. SYSTEM FILES The following files are required to be present for the system to function correctly: MBUSER.EXE - The User interface to the Mailbox MBSYSOP.EXE - The Sysop interface to the Mailbox MBFWD.EXE - The Forwarding system of the Mailbox MBLISTEN.EXE - The system watchdog. Watches ports and hands off the task to the appropriate interface. SERVER.EXE - The server function. This is a general server interface and must be running at all times for the system to function. All functions such as forwarding and housekeeping events are controlled by SERVER.EXE. Server has a command line option that controls which events are displayed in the Server window. Setting the option turns off the the display of these events. To turn off the display of message and login/logout events use "SERVER LM". The LM would be placed on the optional parameters line in the DesqView window that calls SERVER .EXE. (2) The classes of events that are displayed in the SERVER window are: c - Cron events h - Housekeeping events l - Login/Logout events m - message events s - Server activations MBINIT.EXE - The Mailbox initialization program. The program loads global data into LM, checks that the TNC's are alive and provides other startup functions. This must be run prior to Desqview. LM.COM - The Mailbox "Lock Manager", which becomes resident at system startup and provides various services to the MailBox. This program must be loaded prior to the start of DesqView and prior to running MBINIT. YTNC.COM - G8BPQ backend. Required to run system. (See YTNC.DOC for configuration information.) Must be run prior to running DesqView and after running BPQCODE. BPQCODE.EXE - G8BPQ switch interface to your KISS TNC's. This is the required interface for your com ports and must be run prior to DesqView and MBINIT. MBSTAT.EXE - A separate function that can be run in its own Desqview window. It provides a running display of current MailBox activity. (No longer needed for Version 18.1. This is now part of mbsysop.) OPTIONAL FILES NW.EXE - The Netwalker. A tool for tracing connectivity of a NET/ROM or TheNet network. This is now a standalone program. Requires BPQ switch, ytnc and nw to run. RECOVER.EXE - Message and user database recovery program. To ONLY be used in the event of a system crash. PRTLOG.EXE - The MailBox log file analyzer. Will produce summary reports of the mailbox activity. WPOPT.EXE - WP database optimizer. Will sort the WP.MB file which will make some WP database queries faster. WPSTAT.EXE - Provides some statistics on the WP database sturcture. It is mainly used to provide diagnostic information. SHAKE.EXE - Executable files used to maintain the "cookie" database. BAKE.EXE TAKE.EXE FT.EXE - File transfer utility. Is a small add on and is called as a G8BPQ Application. Will transfer executable files without conversion. See FT.DOC for information. HLOC.EXE - A Hierarchial Location utility. Does a dump of the WP.MB (3) file and displays calls seen at different H Addresses. RT.EXE - Round Table utility. Allows users to converse directly with other users in a round table type fashion. This is also called as a G8BPQ Application. See RT.DOC for information. MON.EXE - Monitor utility. Run as a separate window under DesqView. This utility allows the monitoring of channel activity. PRTBPQ.EXE - A G8BPQ utility that displays information on the activity and current status of the G8BPQ Switch. Used mainly as a diagnostic tool. CVTMB.EXE - Utility to convert the database files to a new format when it is required because of new database changes. When installing new version run this program before starting system. WPLOAD.EXE - Utility to load wp information from a text file. SERVERS See SERVER.DOC for more information on SERVERS. ECHO - Created by W0RLI, returns a message. FILEX - Created by W0RLI, provides REQFIL, REQDIR and upload functions. LSTSRV - Created by W0RLI, general mail exploder. REQCB - Created by W0RLI, for the J-COMM and RT Systems Callbook databases. REQDIR - Created by WB3AFL, Directory retreival server. REQFIL - Created by WB3AFL, File retreival server. REQWP - Created by W0RLI, remote queries to WP database. SMTP - Created by K3MC, provides Mailbox/SMTP message interchange. REDIST - Created by W0RLI, Message Redistribution server. CONFIGURABLE FILES The Placement of these files is under control of environmental variable RLICFG. See the OTHER FILES section below for more information. PORTS.MB - MailBox port configuration file. Defines how ports are to behave once the system has started. This is a required file and must be edited for your system. It is read and loaded by MBINIT.EXE. INIT.MB - MailBox initalization file. Contains the system information that is date dependent, wp update path and various system parameters. This is a required file and must be edited for your system. It is read by MBINIT.EXE. Removal of the lines in this file will result in the system not running properly. MOTD.MB - User login file. Contain the user login greeting. It is a required file. It must be edited for your system and can contain globals. NEWUSER.MB - Contains message text file for new user upon first login to the MailBox. (4) INFO.MB - Contains information on the system and is retreived by the I command from the MailBox prompt. XLATE.MB - Translation file that contains information on different types and classes for messages and how to process them. Contains information on Bulletin time-to-live, Holds, Translations, messages to file and message readdress. See SYSOP.DOC for information. DIRS.MB - File that contains information on various subdirectories below \BBS for files and how these directories can be accessed. See SYSOP.DOC for information. TEXT.MB - The file that contains the various prompts and messages that the user and sysop will see. It is a required file and can be edited to suit your site. Do not eliminate any lines from this file. All are required. See SYSOP .DOC for information. FWD.MB - The forwarding file. Contains information on who and what you intend to forward to other systems. Completely configurable. See SYSOP.DOC for information. CRON.MB - The event timer file. This file is required in order for the system to perform any housekeeping or forwarding. This file is intimately tied to SERVER.EXE and FWD.MB and directs the SERVER on when to perform the various MailBox tasks. See SYSOP.DOC for information. SERVER.MB - SERVER Configuration file. Calls the various servers based upon the type of server being used. User configurable and each type is seperated by a blank line. See SYSOP.DOC for information. Server is responsible for the processing of incoming messages. Once a message is received SERVER.MB is scanned for any processing of the message that is needed and then directs the appropriate server to immediately commence that processing. DIST.MB - Message distribuiton file. Contains information on type of message to be distributed and to which callsign or callsigns. Can be completely configured for your location and eliminates the need to place flood designators in FWD.MB. FTUSERS.MB - The file that contains priviledge information for users of the file transfer utility. TAG.MB - The file that contains tag lines for messages that are received by callsign, sent by the sysop or to a callsign. KEYS.MB - Defines sysop users, priviledges and passwords if required for remote sysop activity. Can also be used to provide security for user access. (5) HELP.MB - The file containing the various help texts when called from the MailBox command line. Can be modified to suit your location or users. REDIST.MB - The file containing the definitions of the distribution domains at this system. Defines locbbs, local, region and nation domains for the redistribution of messages. NON-CONFIGURABLE FILES The placement of these files is under control of environmental variable RLIDB. See the OTHER FILES section below for more information. MAIL.MB - Mail file database. Is created by the system and is not user configurable. WP.MB - WP (White Pages) database file. This file contains the user addresses and information. It is created by the system and is updated by user login, message receipt or update by other WP Update files. The information can be editied by the sysop from the Mailbox command prompt. LOGIN.MB - File containing callsigns of logins to the system. Viewed by the J command from the MailBox command line. BID.MB - File containing the BID's (Bulletin Identifer's) of messages received by the system. This file is reviewed by the system upon presentation of a message and determines whether it has seen the file before based upon its presented BID. A parameter in INIT.mb determines how long BIDS are held by the system. MID.MB - Serves the same function as BID.MB except that it monitors personal messages for duplicates. The placement of these files is under control of environmental variable RLILOG. See the OTHER FILES section below for more information. YYMM.LOG - Log files. Created by the system that records the events happening in the system. The files are created upon opening a new Mailbox task. The files are named based on the Year and month. These new log files contain all the information for all events of the system in a single file. OTHER FILES TEMPORARY FILES The placement of these files is under control of environmental variable RLITMP. There are the various temporary files used by the MailBox. These files will reside in the \TMP or other directory as directed by the environmental variable RLITMP. These files are files that are used by the system to import and export the various type of files as they are processed by the system. Examples of these are import/export files used by the server. CONFIG.SYS - Your system config.sys file. It will be necessary to add parameters to this file so that the system can handle the Mailbox. (6) The recommended parameters are: Files=70 Roughly 8 - 10 per open window. Buffers=60 Set this as required by the cache that you use. Stacks=9,256 You may need 16,64, 0,0 or 8,128 depending on your DOS version. In later versions of DOS you can add: Install=C:\dos\share.exe AUTOEXEC.BAT - The auto execution file required for proper automatic system startup. It will be necessary to add the time environmental variable TZ to your AUTOEXEC.BAT ile. This variable is defined as your local time zone (PST, CST, MST or EST), plus your offset in hrs from UTC (8,7,6,5), plus an alternate daylight savings time name. It defaults to PST8PDT so your parameters will depend on your location in relation to UTC. Add the following to this file: Share /L:30 If not loaded in config.sys lm Load the MailBox Lock Manager bpqcode Load the G8BPQ Switch ytnc 20 2 1 Required for versions 4.05 or later of the BPQ Switch. mbinit Initialize the MailBox dv Load DesqView (if using it) Starting in Version 16.8 you may add environmental variables to your autoexec.bat file to set the directory where the different Mailbox files will reside. The four variables are: set TZ=PST8PDT (Default) RLILOG - Directory where the log files will be put RLITMP - Directory where the temp files will go. RLIDB - Directory where the various database files go: BID.MB, LOGIN.MB, MAIL.MB and WP.MB RLICFG - Directory where the configuration files go. CRON, DIRS, DIST, FTUSERS, FWD, HELP, INFO, INIT, KEYS, MOTD, NEWUSER, PORTS, SERVER, TAG, TEXT and XLATE.MB In Autoexec.bat add: set RLILOG=\logs set RLITMP=\tmp set RLIDB=\bbsdb set RLICFG=\bbscfg Note: the above are examples and the directories that you use will have to be created prior to running the system. (7) DISK CACHES It is a good idea to run a disk cache on a your system as the MailBox can be quite disk intensive. SMARTDRV, HYPERDISK, NORTON CACHE or other popular disk caches seem to work well. If you enable "Delayed write" the system will speed up quite considerably. Determining the cache size is at the discretion of the sysop. A 1mb cache is probably a good size to use. However, if you run a large system and have the available memory then a larger cache would be desirable for optimal processing. The optimal cache size would be sum of the files that reside in the directory specified by RLIDB. DESQVIEW AND WINDOW SIZES The approximate window sizes in DesqView for the various programs are: FT - 42k RT - 57k MBUSER - 66k MBSYSOP - 80k MBLISTEN - 29k MBFWD - 46k MBSTAT - 24k Not required for version 18.1 MON - 40k NW - 43 - 100k SERVER - 84k UPGRADING FROM PREVIOUS VERSIONS If you are upgrading from a previous version after version 16.0 you will need to copy the executable files into the directory where your executables are placed. A general procedure is as follows: 1. Backup your system 2. Create a temporary directory and copy the relase file into it. 3. Execute the file that will expand the various files from the archieve. (Normally named MB1608.exe indicating version 16.8) 4. Move or copy the .EXE and .COM files into the directory where they will reside (Except the release archieve file) as specified. 5. Review the example *.mb files and read CHANGES.DOC for any changes that have been made. Pay special attention to CRON.MB, INIT.MB, XLATE.MB, SERVER.MB, DIRS.MB, FWD.MB and TEXT.MB. You will need to modify these files as per section 6 below. 6. In version 18.x INIT.MB will require changes. a. INIT.MB For version 18.0 you will be required to add a YES/NO toggle for use of Grid Square regional type forwarding. This is similar to the toggle for the use of "#" preceeded regional designators. b. Add yes/no toggle for header diagnostics c. SERVER.MB will require that the the size be reduced from 92k to 84k. d. Remove the Init.mb line referencing MBSTAT. (NOTE: YOU WILL HAVE TO HAVE DESQVIEW VERSION 2.5 OR ABOVE TO RUN THIS VERSION) 7. Modify the program sizes to the suggested values above using the Desqview Change a Program (CP) If you are upgrading from 11.0 to version 15.8 follow the above procedure except that you will need to create CRON.MB and run SERVER.EXE in a newly (8) created DesqView window. SERVER.EXE will require a 84K window to run. In some cases you will also have to create KEYS.MB, DIST.MB, XLATE.MB, TEXT.MB and DIRS.MB. If this is the case XLATE, TEXT and DIRS.MB are created from the old CONFIG.MB file. Once these files have been created CONFIG.MB can be deleted. If you are upgrading from a version previous to VERSION 11.0 you will need to convert your WP DATABASE before beginning the upgrade process. Please follow this procedure: 1. From the MailBox prompt issue the command to dump your WP database to a text file. IA WP.TXT 2. Bring down the system. 3. Delete or rename your old WP Database. Then proceed with the procedures as outlined above. After starting the system and it is up and running, from a DOS window issue the command: WPLOAD WP.TXT This will read in your wp data to the new file format. Depending on the size of your WP file this could take some time. If anything fails to run then review the above procedures. Generally failure to run properly can be attributed to imporper window size in DesqView, additional or deleted lines in any of the configurable files (*.MB) or improper commands in PORTS or FWD.MB. INSTALLING A NEW SYSTEM If you are installing a new system then you will be required to do the following: 1. Create the \BBS under the root directory. 2. Make a temporary directory and copy the release file into it and expand the archieve file. 3. Move or copy the executable files (*.COM and *.EXE) files into where you intend for them to reside. 4. Move or copy HELP.MB into the directory where you intend for it to reside. 5. Move or copy the *.mb files into the directory where you intend for them to reside or as defined by the environmental variable RLICFG. 6. Modify or create TEXT.MB, XLATE.MB, DIRS.MB, FWD.MB, CRON.MB, INIT.MB, KEYS.MB, DIST.MB, MOTD.MB, NEWUSER.MB, INFO.MB and PORTS.MB. 7. Modify CONFIG.SYS and AUTOEXEC.BAT to support the MailBox. 8. Place the G8BPQ switch code files in a separate directory under the root directory. 9. Modify the G8BPQ configuration file BPQCFG.TXT for your site and the number of ports that you intend to use. Then compile it using the BPQCFG.EXE file. 10. Configure your TNC's to run in the KISS mode. Note: Kantronics KPC-4 and KAM require Firmware version 2.85 or later. TNC2 or clones should have firmware version 1.1.5 or later. TNC1 should be run no faster than 4800 baud. Note: See the various .SET files included with the release for more information. 11. Once this is done then attempt to start the system. If you have been successfull the last thing that you should see is "MAILBOX INITIALIZED" (9) 12. Bring up Desqview. 13. Create a program item for each part of the Mailbox you intend to run. The minumum is SERVER.EXE. (Note that sample .DVP files are provided.) 14. Close down the system using the SD command. 15. Create a Desqview Script to bring up the various Mailbox tasks in the order you want to come up in with SERVER.EXE as the first task then any other tasks that you may want to run. (See the DesqVIEW manual about creating and saving scripts files.) Save your script file. Modify autoexec.bat to call DV.BAT and restart your system. IN CASE OF A CRASH If the system crashes, make sure that all mailbox tasks are shut down. When you have assured that all is not running run the following files: c:\dos\Checkdsk /f (for DOS 6.x systems run SCANDISK.) c:\bbs\recover.exe c:\bbs\mbinit.exe This will recover your data and ensure that there is not any data loss. DESQVIEW AND QEMM For Version 17.x it will be required to create PIF files for the various components of the system. The PIF files are named in the format of XX-PIF.DVP where XX is the keys used to call the program from the Desqview open window menu. Before creating the necessary .DVP files it will be necessary to setup Desqview to run the Mailbox. NOTE: For version 17.x you will be required to have Desqview version 2.5 or above. 1) Using DESQview SETUP: Under performance: Set the swapping time slices: For 6 Mhz AT, try 6 foreground and 6 background. For 25 Mhz 386/486, try 3 foreground and 3 background. Common Memory 40 Dos buffer for EMS 15 Optimize communications N Allow Swapping of programs Y Manage printer contention N Under Logical drives: logical drives: none swap drives : none Under video monitor: video monitor : for EGA use 3....CGA option for color gives maximum memory. Mono is the best for memory and yields the maximum conventional memory after optimization. (10) display text/graphics Y if you want the screen blanker to work. Monitor require sych access N Screen blanker What ever is appropriate. If disp text graphics not set to y then it will not work. 2) Setting Up the PIF Files From the Desqview open window menu you will need to use the add a program portion of Desqview. Enter the AP command, space to other and enter the space bar to select. When the prompt for directory put in \mbexe and then <cr>. Enter the information as outlined above for the first section, then F10 for the advanced options. A <CR> at this point will return you to the Add a Program menu. Again go to other and enter the space bar. Add all the programs necessary for the system including your text editor and all the server options that you intend to run. Program Name: MAILBOX: MBSYSOP.EXE Key to use on open menu: MS (Anything you like) Note: It is very benifical to use keys that approximate the program that you are going to start. This might require that some of the existing keys be redefined. For instance Desqview Manifest uses MF to call the Manifest program. Redefining this to another key sequence will allow you to use MF to call MBFWD with the MF keys. Memory Size (in K): 75 (or the appropriate size as defined previously) Program: MBSYSOP.EXE Parameters: (Leave this blank except where required) Directory: C:\MBEXE (Where you put your .EXE and .COM files.) Writes directly to screen: N Displays graphics information: N Virtualize text/graphics N Uses serial ports (Y,N,1,2) N Requires floppy diskette: N ADVANCED OPTIONS: <F10> System Memory: 0 Maximum Program Memory Size: Script Buffer Size: 1000 Max Expanded Memory Size: Text Pages: 1 Graphics Pages: 0 Interrupts: 00 to FF Close on exit: Y Uses own colors: N Allow close window command: Y Runs in Background: Y Uses math co-processor: N Keyboard Conflict: 0 Share CPU when foreground: Y Share EGA when fore/zoomed Y for EGA only setting. N for monochrome will yield about 30k more convention memory. Can be swapped out: N Protection level 0 <- Normally 0. Some systems may require this be set to 1. (11) 3) Using the Included PIF Files To use the included PIF files you will need to copy or move these files into the directory where the .EXE and .COM files will reside (Example: \mbexe). From the Add a Program menu select OTHER and then <cr> and the files will be displayed in a submenu. Select all of the files and then <CR>. At this time it would be appropriate to review all of the files using the Change a Program file to make sure that the appropriate directory has be detailed on the directory line. Change as required. If there is a key stroke conflict you will be warned and will be required to change them before the process will be complete. 4) QEMM It is recommended that QEMM be used in conjunction with Desqview. The use of QEMM will give you the capability to access additional memory in the extended memory range of A000 - FFFF for TSR's and the added capability of exapnded memory for running the Mailbox and its many tasks. Installing QEMM will normally place the following line in your CONFIG.SYS file: DEVICE=C:\QEMM\QEMM386.SYS RAM This will load the expanded memory manager and allow access to memory above the FFFF or 1024kb area. The use of the QEMM OPTIMIZATION routine will further increase your systems capabilities be allowing QEMM to place many of your TSR's and programs into the blank memory spaces between A000 - FFFF (640k - 1024k). On a typical system this will increase the conventional memory available for DOS from 550k to well over 600K. In the case of a monochrome system this number could be as high as 721k. The optimization routine will automatically attempt to place your TSR's into the extended memory area, and if successfull, will modify your config.sys and autoexec.bat files with statements such as LOADHI c:\bpq\bpqcode. A command line option for QEMM called MAPS should be set to a number higher than the number of DV windows you will run. If you will run 15 windows you should add the command line option MAPS=17 (or larger). This is done in config.sys to the qemm device line. For example: DEVICE=C:\QEMM\QEMM386.SYS RAM MAPS=17 Just one word of caution. When running QEMM or other memory managers it is required to re-optimize the system when installing or upgrading any compontent of the MailBox. This will ensure that programs will not contend for the same piece of memory resulting in a system crash. (12)